---
title: Inclusive
redirect_from:
  - /content/voice-tone/inclusive/
---

import { Illustration } from "@kiwicom/orbit-components";

<Illustration name="Success" alt="" size="display" />

We treat everyone with **respect** and **without prejudice**.
Our diversity and inclusivity is our **strength**:
it allows us to have ideas and solve problems from different perspectives
and it increases competitiveness, creativity, and collaboration.

## Use cross-cultural expressions

Write to be understood **no matter what** the reader's cultural background is.
Your content might be read by people who might be reading English
as a second (or third or fourth ...) language and it might be translated.

### Minimize your use of idioms

Idioms are often based on a particular culture
and tend not be hard for people from other cultures to understand.
Write using more **universal language**.

<GuidelinesSideBySide>

<Do>

- The possibilities for your travels are endless.
- To get to the point, it's your decision now.
- It might look like a good deal, but that's only because it's stolen.

</Do>

<Dont>

- The sky's the limit for your travels.
- To cut to the chase, the ball's in your court now.
- It might look like a real bargain, but that's only because it fell off the back of a lorry.

</Dont>

</GuidelinesSideBySide>

### Avoid slang

Slang can be harder for people with English as a second language to understand.

<GuidelinesSideBySide>

<Do>

- We'll answer you very soon.
- You only get one life, so get out of your neighborhood and explore the world.

</Do>

<Dont>

- We're gonna answer you real soon.
- YOLO, so get outta your bitz and explore the world.

</Dont>

</GuidelinesSideBySide>

## Be inclusive

We write so everyone feels a part of what we're saying.
Make sure your writing includes everyone in its defaults.

### Use gender-neutral language

Using language that sets the default to male can make people feel excluded.
Use terms that include everyone, such as genderless terms.
Feel free to use "they" in the singular for people of unknown gender.

<GuidelinesSideBySide>

<Do>

- After users log in, they see a welcome screen.
- Everyone, come and join the fun!
- flight attendant

</Do>

<Dont>

- After the user logs in, he sees a welcome screen
- Guys, come and join the fun!
- steward/stewardess

</Dont>

</GuidelinesSideBySide>

### Focus on people, not characteristics

When describing people, put the people first.
Make exceptions for groups who prefer identity-first descriptions.

<GuidelinesSideBySide>

<Do>

- People with disabilities
- People without disabilities
- A Deaf person

</Do>

<Dont>

- The disabled
- Normal people
- A person with deafness

</Dont>

</GuidelinesSideBySide>

## Write accessibly

Make sure everything you write is [accessible](/foundation/accessibility/) to everyone.
Remember that **not everyone sees** your visual content,
so communicate the message in **various ways**.

- Include various **fallbacks** for your content.
- Use emojis/images/and so on to make your textual content **more interesting**,
  but **don't replace** words.
